Status. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Fixes an issue in which a SHARING VIOLATION error "Error 6518, Severity 16, State 2" occurs on the microsoft.sqlserver.types.dll assembly in SQL Server 2012 or SQL Server 2014.

Fixes an issue in which the MSBuild rebuilds unchanged IDL files unexpectedly. This issue occurs when you use the Visual Studio x64 Win64 Command Prompt in Visual Studio 2010 to rebuild a Visual C++ project.

When you run a client application that uses the Microsoft.SqlServer.Types.dll component on a computer that has Microsoft SQL Server 2008 Service Pack 2 (SP2) installed, you receive the following error message: Unable to load DLL 'SqlServerSpatial.dll' Exception from HRESULT 0xE06D7363.

Symptoms. When you build a Visual C++ project in Visual Studio 2013 Update 5 that uses certain types from a .NET assembly, you may receive the following error message: fatal error C1001: An internal error has occurred in the compiler. (compiler file 'f:\dd\vctools\compiler\cxxfe\sl\p1\c\esu.c', line 6378)

Microsoft has adopted many strategies to help protect customers from threats that could be delivered in these types of files without losing the benefits that these file types offer. Microsoft customers should be aware that opening unsafe types of files could cause malicious damage to computer systems. These files could contain viruses or Trojan ...

Provides an overview of unsafe file types in Microsoft products. Lists Microsoft products that include safeguards to help protect customers from unsafe file types.

When you open a screen in Microsoft Dynamics SL 7.0, in Microsoft Dynamics SL 6.5, or in Microsoft Business Solutions - Solomon 6.0, you may receive the following error message: Programming Bulletproof Error 10260 - Table % does not have a TimeStamp Column, please add a TimeStamp Column to the table.

Describes a hotfix that enables you to use Package Installation Wizard (Dtsinstall.exe) to run the deployment manifest file of an SSIS package when SSIS 2008 or SSIS 2008 R2 is not installed.

To provide the hotfix for when the Manifest Entry (40.115.00) screen allows for "Shipping Confirmed" when there's insufficient inventory, even though the Shippers (40.110.00) screen produces System Message 6678 in Microsoft Dynamics SL.

Resolution. To resolve this problem, use the appropriate method. Method 1: Manually register the Capicom.dll file. To do this, follow these steps: NOTE This resolution does NOT apply to Microsoft Dynamics SL 2011. Locate and then open the Windows\System32 folder. Right-click the Capicom.dll file, and then click Open With.